-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(workspace): Distribute pipeline, not providers #717
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a proponent of this refactor. Left a few comments that I'd like to see addressed prior to merging.
I'd also like to get this in first: #713 |
c817d72
to
2e88e14
Compare
3e59c5a
to
ba3c337
Compare
ba3c337
to
aed7355
Compare
* feat(workspace): Distribute pipeline, not providers * lint
Overview
Experiment to distribute
DerivationPipeline
types, askona-providers-alloy
is doing today. Our abstractions are a bit off right now, withkona-providers
holding traits specific tokona-derive
, without ever needing to be used alongside it. However,kona-providers-alloy
is already following a great pattern by distributing the pipeline itself with a constructor for the configuration asnew_online_pipeline
, as the abstractions intended.This pattern keeps cyclical dependencies away, and because we're distributing the pipeline, there's no real need for
kona-providers
. We can also extend this pattern further, with a good cleanup of the oracle-backed pipeline into a newkona-derive-oracle
crate.This is also how modifications like alt DA intend to ship their pipeline type variants as well.